SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Bootstrap Protocol</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Bootstrap Protocol</span></span>

</h1>

</header>

<p>The <b>Bootstrap Protocol</b> (<b>BOOTP</b>) is a computer networking protocol used in

<a href="Internet_Protocol" title="Internet Protocol">Internet Protocol</a> networks to automatically assign an <a href="IP_address" title="IP address">IP address</a> to network devices from a configuration server. The BOOTP was originally defined in <style data-mw-deduplicate="TemplateStyles:r1238218222">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc951">951</a> published in 1985.

</p><p>While some parts of BOOTP have been effectively superseded by the <a href="Dynamic_Host_Configuration_Protocol" title="Dynamic Host Configuration Protocol">Dynamic Host Configuration Protocol</a> (DHCP), which adds the feature of leases, parts of BOOTP are used to provide service to the DHCP protocol. Some DHCP servers also provide the legacy BOOTP functionality.

</p><p>When a network-connected computer <a href="Booting" title="Booting">boots</a> up, its IP stack broadcasts BOOTP network messages requesting an IP address assignment. A BOOTP configuration server replies to the request by assigning an IP address from a pool of addresses, which is preconfigured by an administrator.

</p><p>BOOTP is implemented using the <a href="User_Datagram_Protocol" title="User Datagram Protocol">User Datagram Protocol</a> (UDP) for transport. Port number 67 is used by the server for receiving client requests, and port number 68 is used by the client for receiving server responses. BOOTP operates only on <a href="IPv4" title="IPv4">IPv4</a> networks.

</p><p>Historically, BOOTP has also been used for <a href="Unix-like" title="Unix-like">Unix-like</a> <a href="Diskless_workstation" class="mw-redirect" title="Diskless workstation">diskless workstations</a> to obtain the network location of their <a href="Boot_image" title="Boot image">boot image</a>, in addition to the IP address assignment. Enterprises used it to roll out a pre-configured client (e.g., <a href="Microsoft_Windows" title="Microsoft Windows">Windows</a>) installation to newly installed PCs.

</p><p>Initially requiring the use of a boot <a href="Floppy_disk" title="Floppy disk">floppy disk</a> to establish the initial network connection, manufacturers of network interfaces later embedded the protocol in the <a href="Firmware" title="Firmware">firmware</a> of interface cards as well as system boards with on-board network interfaces, thus allowing direct network booting.

</p>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

<p>The BOOTP was first defined in September 1985 by Bill Croft and <a href="John_Gilmore_(activist)" title="John Gilmore (activist)">John Gilmore</a><sup id="cite_ref-rfc951_1-0" class="reference"><a href="#cite_note-rfc951-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> as a replacement for the <a href="Reverse_Address_Resolution_Protocol" title="Reverse Address Resolution Protocol">Reverse Address Resolution Protocol</a> (RARP), published in June 1984.<sup id="cite_ref-rfc903_2-0" class="reference"><a href="#cite_note-rfc903-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> The primary motivation for replacing RARP with BOOTP is that RARP was a <a href="Link_layer" title="Link layer">link layer</a> protocol. This made implementation difficult on many server platforms, and required that a server be present on each individual IP <a href="Subnetwork" class="mw-redirect" title="Subnetwork">subnet</a>. BOOTP introduced the innovation of relay agents, which forwarded BOOTP packets from the local network using standard IP routing, so that one central BOOTP server could serve hosts on many subnets.<sup id="cite_ref-rfc951_1-1" class="reference"><a href="#cite_note-rfc951-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup><sup class="reference nowrap"><span title="Location: §6">: §6 </span></sup>

</p><p>An increasing set of BOOTP vendor information extensions was defined<sup id="cite_ref-rfc1048_3-0" class="reference"><a href="#cite_note-rfc1048-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-rfc1084_4-0" class="reference"><a href="#cite_note-rfc1084-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-rfc1395_5-0" class="reference"><a href="#cite_note-rfc1395-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-rfc1497_6-0" class="reference"><a href="#cite_note-rfc1497-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup> to supply BOOTP clients of relevant information about the network, like <a href="Default_gateway" title="Default gateway">default gateway</a>, <a href="Domain_name_system" class="mw-redirect" title="Domain name system">name server IP address</a>, the <a href="Domain_name" title="Domain name">domain name</a>, etcetera.

</p><p>With the advent of the <a href="Dynamic_Host_Configuration_Protocol" title="Dynamic Host Configuration Protocol">Dynamic Host Configuration Protocol</a>, the BOOTP vendor information extensions were incorporated as DHCP option fields,<sup id="cite_ref-rfc1533_7-0" class="reference"><a href="#cite_note-rfc1533-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-rfc2132_8-0" class="reference"><a href="#cite_note-rfc2132-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> to allow DHCP servers to also serve BOOTP clients.

</p>

<div class="mw-heading mw-heading2"><h2 id="Operation">Operation</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Case_1:_Client_and_server_on_same_network">Case 1: Client and server on same network</h3></div>

<p>When a BOOTP client is started, it has no IP address, so it broadcasts a message containing its MAC address onto the network. This message is called a “BOOTP request”, and it is picked up by the BOOTP server, which replies to the client with the following information that the client needs:

</p>

<ol><li>The client's IP address, subnet mask, and default gateway address.</li>

<li>The IP address and host name of the BOOTP server.</li>

<li>The IP address of the server that has the boot image, which the client needs to load its operating system.</li></ol>

<p>When the client receives this information from the BOOTP server, it configures and initializes its TCP/IP protocol stack, and then connects to the server on which the boot image is shared. The client loads the boot image and uses this information to load and start its operating system.<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup>

</p><p>The Dynamic Host Configuration Protocol (DHCP) was developed as an extension of BOOTP. BOOTP is defined in Requests for Comments (RFC) 951 and 1084.

</p>

<div class="mw-heading mw-heading3"><h3 id="Case_2:_Client_and_server_on_different_networks">Case 2: Client and server on different networks</h3></div>

<ol><li>Problem with the bootp request is that the request is broadcast. A <a href="IP_address#Broadcast_addressing" title="IP address">broadcast</a> <a href="IP_datagram" class="mw-redirect" title="IP datagram">IP datagram</a> cannot pass through any router. The router discards this packet.</li>

<li>To solve this problem, there is a need for an intermediary (relay).</li>

<li>One of the host or router can be configured at application layer to operate as relay agent.</li>

<li>The relay agent knows the uni-cast address of bootp server and listens for broadcast message on port 67.</li>

<li>When it receives this broadcast packet, it encapsulates the message in <a href="Unicast" title="Unicast">unicast</a> datagram and sends request to bootp server.</li>

<li>The packet carrying a unicast destination address is routed by any router and reaches the bootp server.</li>

<li>The relay agent, after receiving the reply, sends it to bootp client.</li></ol>

<div class="mw-heading mw-heading2"><h2 id="IETF_standards_documentation">IETF standards documentation</h2></div>

<ul><li><cite id="CITEREFB._Volz2004" class="citation cs1">B. Volz (November 2004). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3942"><i>Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options</i></a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC3942">10.17487/RFC3942</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3942">3942</a>.</cite> <i>Proposed Standard.</i> Updates RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2132">2132</a>.</li>

<li><cite id="CITEREFS._AlexanderR._Droms1997" class="citation cs1">S. Alexander; R. Droms (March 1997). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2132"><i>DHCP Options and BOOTP Vendor Extensions</i></a>. <a href="Internet_Engineering_Task_Force" title="Internet Engineering Task Force">IETF</a> Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC2132">10.17487/RFC2132</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2132">2132</a>.</cite> <i>Draft Standard.</i> Obsoletes RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1533">1533</a>. Updated by RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc3442">3442</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc3942">3942</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc4361">4361</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc4833">4833</a> and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc5494">5494</a>.</li>

<li><cite id="CITEREFW._Wimer1993" class="citation cs1">W. Wimer (October 1993). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1542"><i>Clarifications and Extensions for the Bootstrap Protocol</i></a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1542">10.17487/RFC1542</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1542">1542</a>.</cite> <i>Draft Standard.</i> Updates RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc951">951</a>. Obsoletes RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1532">1532</a>.</li>

<li><cite id="CITEREFR._Droms1993" class="citation cs1">R. Droms (October 1993). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1534"><i>Interoperation Between DHCP and BOOTP</i></a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1534">10.17487/RFC1534</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1534">1534</a>.</cite> <i>Draft Standard.</i></li>

<li><cite id="CITEREFBill_CroftJohn_Gilmore1985" class="citation cs1">Bill Croft; John Gilmore (September 1985). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc951"><i>BOOTSTRAP PROTOCOL (BOOTP)</i></a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC0951">10.17487/RFC0951</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc951">951</a>.</cite> <i>Draft Standard.</i> Updated by RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1395">1395</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1497">1497</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1532">1532</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1542">1542</a> and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc5494">5494</a>.</li></ul>

<ul><li><a href="Preboot_Execution_Environment" title="Preboot Execution Environment">Preboot Execution Environment</a> (PXE)</li>

<li><a href="Remote_Initial_Program_Load" title="Remote Initial Program Load">Remote Initial Program Load</a> (RIPL)</li>

<li><a href="UDP_Helper_Address" title="UDP Helper Address">UDP Helper Address</a> — a tool for routing BOOTP requests across subnet boundaries</li>

<li><a href="Boot_Service_Discovery_Protocol" title="Boot Service Discovery Protocol">Boot Service Discovery Protocol</a> (BSDP)</li>

<li><a href="Maintenance_Operations_Protocol" title="Maintenance Operations Protocol">Maintenance Operations Protocol</a> (MOP)</li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

<li id="cite_note-rfc951-1"><span class="mw-cite-backlink">^ <a href="#cite_ref-rfc951_1-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-rfc951_1-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFBill_CroftJohn_Gilmore1985" class="citation cs1">Bill Croft; John Gilmore (September 1985). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc951"><i>BOOTSTRAP PROTOCOL (BOOTP)</i></a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC0951">10.17487/RFC0951</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc951">951</a>.</cite> <i>Draft Standard.</i> Updated by RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1395">1395</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1497">1497</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1532">1532</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1542">1542</a> and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc5494">5494</a>.

</span>

</li>

<li id="cite_note-rfc903-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-rfc903_2-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFR._FinlaysonT._MannJ._MogulM._Theimer1984" class="citation cs1">R. Finlayson; T. Mann; J. Mogul; M. Theimer (June 1984). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc903"><i>A Reverse Address Resolution Protocol</i></a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC0903">10.17487/RFC0903</a></span>. STD 38. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc903">903</a>.</cite> <i>Internet Standard 38.</i>

</span>

</li>

<li id="cite_note-rfc1048-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-rfc1048_3-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFP._Prindeville1988" class="citation cs1">P. Prindeville (February 1988). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1048"><i>BOOTP Vendor Information Extensions</i></a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1048">10.17487/RFC1048</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1048">1048</a>.</cite> <i>Obsolete.</i> Obsoleted by RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1084">1084</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1395">1395</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1497">1497</a> and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1533">1533</a>.

</span>

</li>

<li id="cite_note-rfc1084-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-rfc1084_4-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFJ._Reynolds1988" class="citation cs1"><a href="Joyce_K._Reynolds" title="Joyce K. Reynolds">J. Reynolds</a> (December 1988). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1084"><i>BOOTP Vendor Information Extensions</i></a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1084">10.17487/RFC1084</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1084">1084</a>.</cite> <i>Obsolete.</i> Obsoleted by RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1395">1395</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1497">1497</a> and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1533">1533</a>. Obsoletes RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1048">1048</a>.

</span>

</li>

<li id="cite_note-rfc1395-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-rfc1395_5-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFJ._Reynolds1993" class="citation cs1"><a href="Joyce_K._Reynolds" title="Joyce K. Reynolds">J. Reynolds</a> (January 1993). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1395"><i>BOOTP Vendor Information Extensions</i></a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1395">10.17487/RFC1395</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1395">1395</a>.</cite> <i>Obsolete.</i> Obsoleted by RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1497">1497</a> and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1533">1533</a>. Obsoletes RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1084">1084</a> and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1048">1048</a>. Updates RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc951">951</a>.

</span>

</li>

<li id="cite_note-rfc1497-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-rfc1497_6-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFJ._Reynolds1993" class="citation cs1"><a href="Joyce_K._Reynolds" title="Joyce K. Reynolds">J. Reynolds</a> (August 1993). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1497"><i>BOOTP Vendor Information Extensions</i></a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1497">10.17487/RFC1497</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1497">1497</a>.</cite> <i>Obsolete.</i> Obsoleted by RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1533">1533</a>. Obsoletes RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1395">1395</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1084">1084</a> and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1048">1048</a>. Updates RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc951">951</a>.

</span>

</li>

<li id="cite_note-rfc1533-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-rfc1533_7-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFS._AlexanderR._Droms1993" class="citation cs1">S. Alexander; R. Droms (October 1993). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1533"><i>DHCP Options and BOOTP Vendor Extensions</i></a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1533">10.17487/RFC1533</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1533">1533</a>.</cite> <i>Obsolete.</i> Obsoleted by RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2132">2132</a>. Obsoletes RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1497">1497</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1395">1395</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1084">1084</a> and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1048">1048</a>.

</span>

</li>

<li id="cite_note-rfc2132-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-rfc2132_8-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFS._AlexanderR._Droms1997" class="citation cs1">S. Alexander; R. Droms (March 1997). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2132"><i>DHCP Options and BOOTP Vendor Extensions</i></a>. <a href="Internet_Engineering_Task_Force" title="Internet Engineering Task Force">IETF</a> Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC2132">10.17487/RFC2132</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2132">2132</a>.</cite> <i>Draft Standard.</i> Obsoletes RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1533">1533</a>. Updated by RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc3442">3442</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc3942">3942</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc4361">4361</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc4833">4833</a> and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc5494">5494</a>.

</span>

</li>

<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://networkencyclopedia.com/bootstrap-protocol-bootp/">"Bootstrap Protocol (BOOTP)"</a>. <i>Network Encyclopedia</i>.</cite></span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a rel="nofollow" class="external text" href="http://www.eventhelix.com/RealtimeMantra/Networking/Bootp.pdf">BOOTP Sequence Diagram</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20150226073404/http://www.eventhelix.com/RealtimeMantra/Networking/Bootp.pdf">Archived</a> 2015-02-26 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> (PDF)</li>

<li><a rel="nofollow" class="external text" href="http://mbootp.sourceforge.net/">Multicast BOOTP for configuring a network device</a></li>

<li><a rel="nofollow" class="external text" href="http://mbootp.sourceforge.net/">Multicast BOOTP server and client</a></li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-06-18" href="https://en.wikipedia.org/wiki/?title=Bootstrap_Protocol&oldid=1296235090">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>